Systems &amp; methods for smart content streaming

ABSTRACT

Systems and methods for providing an authenticated groupcast stream of content to destination receivers are disclosed. A method may include receiving information indicating that a media capturing source(s) located at a premises and destination receivers are included in a group. Content captured from a media capturing source(s) may be received. The content may include an image(s)/video(s) and a destination network address associated with the destination receivers. The content may be copied. The number of copies of content may correspond to a number of the destination receivers. A respective copy of the content may be sent to the destination receivers.

BACKGROUND

In some conventional wireless systems, entities associated with a homenetwork may request content captured from cameras of the home. Thecameras of the home typically need to simultaneously provide multiplestreams of the same captured content to requesting entities. However,home cameras generating and sending multiple copies of the same contentstreams simultaneously to different requesting entities may undesirablydrain and consume computing resources such as processing and memorycapacity of the cameras. The draining of the computing resources of thecameras may slowdown operation of the cameras resulting in anundesirable user experience (e.g., lag, distorted images/videos, etc.).In view of these and other shortcomings, there is a need for an improvedsystem.

SUMMARY

Systems and methods are described for providing an authenticated streamof content to one or more destination receiver entities. The system maycomprise one or more media capturing sources (e.g., cameras, videorecording devices, etc.) of a premises (e.g., a home, building, office,warehouse, store, etc.) or an outdoor space (e.g., backyard, park,etc.), and one or more devices and/or services (e.g., destinationreceiver entities) associated with a network. The devices and/orservices may desire to receive the content captured by a media capturingsource(s).

The one or more media capturing sources and the one or more receivingdevices and/or services may register with a smart premises video groupauthentication service provided by a network (e.g., a network device) tojoin a group. Based on registering with the smart premises video groupauthentication service, the network may generate group informationindicating the registered media capturing sources and devices and/orservices that joined the group. The smart premises video groupauthentication service may provide (e.g., via a network device) thegroup information to a gateway device located at a premises, that isconnected to a registered media capturing source(s).

When the registered media capturing source(s) captures content, themedia capturing source(s) may send the captured content and associateddata (e.g., in a datagram) in a content stream (e.g., a single stream)to a communication device. The communication device may duplicate/copythe stream based in part on the number/quantity of registered devicesand/or services and may send a duplicated stream to each of theregistered devices and/or services of a group.

In an aspect, methods may comprise receiving information indicating thata media capture source, located at a premises, and one or moredestination entities are included in a group. Content comprising acaptured image or video and an indication of a destination networkaddress may be received from the media capture source. The destinationnetwork address may be associated with the one or more destinationentities of the group. The destination network address may be used todetermine network addresses of the one or more destination entities. Oneor more copies of the content may be created. The number of the copiesof content may correspond to a number of the one or more destinationentities. A respective copy of the copies of the content may be sent toone or more destination entities of the group determined to receive thecontent.

In another aspect, methods may comprise receiving, from a media capturesource, content comprising a captured image or video and an indicationof a destination network address. The destination network address may beassociated with one or more destination entities of a group. Thedestination network address may be used to determine one or more networkaddresses of the one or more destination entities. One or more copies ofthe content may be created. The number of the copies of content maycorrespond to a number of the network addresses of the one or moredestination entities of the group determined to receive the content. Arespective copy of the copies of the content may be sent to one or moredestination entities of the group determined to receive the content.

In yet another aspect, methods may comprise receiving one or morerequests from a media capture source and one or more destinationentities to register with a service and to join a group. Content may bereceived from the media capture source. The content may comprise acaptured image or video and an indication of a destination networkaddress associated with the one or more destination entities of thegroup. The destination network address may be used to determine one ormore network addresses of the one or more destination entities. One ormore copies of the content may be created. The number of copies of thecontent may correspond to a number of the network addresses of the oneor more destination entities of the group determined to receive thecontent. A respective copy of the copies of the content may be sent toone or more destination entities of the group determined to receive thecontent.

Additional advantages will be set forth in part in the description whichfollows or may be learned by practice. The advantages will be realizedand attained by means of the elements and combinations particularlypointed out in the appended claims. It is to be understood that both theforegoing general description and the following detailed description areexemplary and explanatory only and are not restrictive, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate embodiments and together with thedescription, serve to explain the principles of the methods and systems:

FIG. 1 is a block diagram of an example system and network;

FIG. 2 is a block diagram of an example system;

FIG. 3 is a diagram of an example data structure of a datagram;

FIG. 4 is diagram of an example Internet Protocol (IP) header of adatagram;

FIG. 5 is a diagram of an example data structure of options data of anIP header;

FIG. 6 is a diagram of an example table illustrating group destinationIP addresses and individual destination IP addresses;

FIG. 7 is a diagram of an example IP header of a datagram;

FIG. 8 is a diagram of an example table illustrating group destinationIP addresses and individual destination IP addresses;

FIG. 9 is a diagram of an example IP header of a datagram;

FIG. 10 is a diagram of an example IP header of a datagram;

FIG. 11 is a diagram of an example IP header of a datagram;

FIG. 12 is a flow chart of an example method;

FIG. 13 is a flow chart of an example method;

FIG. 14 is a flow chart of an example method; and

FIG. 15 is a block diagram of an example computing system.

DETAILED DESCRIPTION

As referred to herein a groupcast may be a stream of one or more copiesof content (e.g., an image(s)/video(s) and associated audio) sent to agroup of registered receiver entities. In some examples, the copies ofcontent may be sent simultaneously to the group of registered receiverentities. In other examples, the copies of content may be sent atdifferent instances/times to the registered destination receiverentities.

Systems and methods are described for providing an authenticatedgroupcast stream of content to one or more destination receiverentities. The groupcast stream of content may include a duplicate/copyof content (e.g., an image(s)/video(s)) captured by a media capturingsource of a premises.

For instance, the system may comprise one or more media capturingsources (e.g., cameras, video recording devices, etc.) of a premises(e.g., a home, building, office, warehouse, store, etc.) and one or moredevices and/or services (e.g., destination receiver entities) associatedwith a network. The devices and/or services may desire to receive thecontent captured by a media capturing source(s). The one or more mediacapturing sources and the one or more devices and/or services (e.g.,destination receivers) may register with a smart premises video groupauthentication service provided by a network (e.g., a network device) tojoin a groupcast group. Based in part on registering with the smartpremises video group authentication service, the network may generateand store group information indicating the registered media capturingsources and devices and/or services that joined the group. The smartpremises video group authentication service may provide (e.g., via anetwork device) the group information to a gateway device located at apremises, that is connected (e.g., via Wi-Fi, Bluetooth, Zigbee, etc.)to a registered media capturing source(s).

In an instance in which the registered media capturing source(s)captures content, the media capturing source(s) may send the capturedcontent and associated data (e.g., a datagram) in a single stream to acommunication device (e.g., the gateway device, a network device). Thecommunication device may duplicate/copy the stream based in part on thenumber/quantity of registered devices and/or services and may send aduplicated stream to each of the registered devices and/or services of agroupcast group.

As pointed out above, in some conventional wireless systems, entitiesassociated with a home network may request content captured from camerasof the home that typically need to simultaneously provide multiplestreams of the same captured content to requesting entities. However,generating multiple copies of the same content streams to sendsimultaneously to different requesting entities may consume the limitedcomputing resources (e.g., processing and memory capacity) of thecameras. Additionally, constraining the computing resources of thecameras by generating multiple streams of the same content may slowdownoperation of the cameras and thereby cause the exchange of data (e.g.,firmware updates, operating system updates, etc.) between the camerasand other devices across a network to constrain the bandwidth resourcesof the network.

The systems and methods described herein providing authenticatedgroupcast stream of content to one or more destination receiver entities(e.g., devices and/or services) may overcome these drawbacks. Forexample, by utilizing a communication device(s) that duplicates/copies astream captured by a media capturing source(s) and sends the duplicatedstream to a registered/authenticated device(s) and/or service(s), thesystems and methods described herein may eliminate a need for a camerato produce multiple streams of content, as exhibited by conventionalsystems, thereby conserving the processing and memory capacity resourcesof cameras. Additionally, the destination receiver entities (e.g.,devices and/or services) of the systems and methods described herein arenot required to establish a peer-to-peer connection to media capturingsources (e.g., cameras), as in some conventional systems, therebyfreeing up bandwidth resources in a network.

FIG. 1 illustrates various aspects of an exemplary network in which thepresent methods and systems may operate. Those skilled in the art willappreciate that present methods may be used in systems that employ bothdigital and analog equipment. One skilled in the art will appreciatethat provided herein is a functional description and that the respectivefunctions can be performed by software, hardware, or a combination ofsoftware and hardware.

A system 100 and network may comprise a camera device 101 (also referredto herein as camera 101), a gateway device 111, a user device 102, acomputing device 104, a computing device 124 and a computing device 134.The camera device 101 and the gateway device 111 may be located at apremises (e.g., premises 119 such as, for example, a home, a building,etc.). In some examples, the user device 102 may be remote/external tothe premises. In other examples, the user device 102 may be located atthe premises. The computing devices 104, 124 and 134 may be networkdevices (e.g., servers) and may be located remote/external to thepremises (e.g., premises 119). The camera device 101, gateway device111, user device 102, computing device 104, computing device 124 andcomputing device 134 may be in communication with each other via anetwork 105 such as, for example, a private or public network (e.g.,Internet). Other forms of communications can be used, such as wired andwireless telecommunication channels, for example. Although FIG. 1 showsthat system 100 includes one camera device 101, one gateway device 111,one user device 102, one computing device 104, one computing device 124and one computing device 134, it should be pointed out that system 100may include any suitable number of camera devices 101, gateway devices111, user devices 102, computing devices 104, computing devices 124 andcomputing devices 134 without departing from the spirit and scope of theinvention.

The camera device 101 (e.g., a camera, a video recording device, etc.)may include a camera module 109 configured to capture one or moreimages, videos (e.g., captured video of movement within the premises,etc.) and corresponding audio data. The camera device 101 may store, viaprocessor 107, the one or more images, videos and/or audio data in thestorage 103. Additionally, the camera device 101 may provide a contentstream (e.g., a single stream) of a captured image/video and associatedaudio to the gateway device 111. The gateway device 111 maycopy/duplicate the content stream and may send the copied content streamto receiver entities (e.g., the user device 102, the live stream module121, the upload service module 130 and/or thumbnail service module 140,as described more fully below.

The gateway device 111 may be a communication device (e.g., a router, amodem) that provides an interface to various entities (e.g., premisesdevices such as, for example, camera devices 101, radio-frequency (RF)sensors, acoustic devices, home automation devices, computers, mobiledevices, etc.) within a premises. The gateway device 111 may beconfigured to act as a gateway interface between devices (e.g., cameradevices 101, etc.) of the premises (e.g., premises 119) and one or morenetwork devices (e.g., computing device 104, computing device 124,computing device 134, etc.).

The gateway device 111 may be coupled to one or more camera devices 101and may receive (e.g., via a single stream) one or more captured imagesand/or videos, as well as associated audio and other data from a cameradevice 101, which may be stored, via processor 117, in storage 115. Thecaptured images/videos and associated audio may be viewable on a displayof the gateway device 111. The one or more camera devices 101 may be incommunication with the gateway device 111 wirelessly (e.g., WiFi,Bluetooth, Zigbee, etc.) or via other connections (e.g., a wirelesslocal area network (WLAN), etc.).

The gateway device 111 may be configured to communicate with thecomputing device 104, the computing device 124, the computing device 134as well as the user device 102 via a network (e.g., network 105 such as,for example, a wide area network (WAN), a cellular network). Broadbandcommunication may be provided by coupling the gateway device 111 withthe wide area network, such as a provider network or the Internet. Insome examples, the gateway device 111 may be configured with a cellularnetwork transceiver that permits communication with a cellular network.The cellular network may provide access to the computing device 104, thecomputing device 124, the computing device 134 and/or user device 102.The gateway device 111 may not be limited to providing gatewayfunctionality via cellular and dwelling-based routers and modems. Thegateway device 111 may be configured with other network protocolcontrollers, such as a controller configured for WorldwideInteroperability for Microwave Access (WiMAX) satellite-based broadband,a controller configured for direct telephone coupling, and the like.

In some examples, the gateway device 111 may determine (e.g., viaprocessor 117) a number of receiver entities registered for anauthentication service (also referred to herein as smart premises videogroup authentication service or smart home video group authenticationservice) and may copy, based on a number/quantity of registered receiverentities, a content stream of an image(s)/video(s) received from acamera device 101. The gateway device 111 may send a content stream ofone or more copies (also referred to herein as a groupcast stream) ofthe image/video received from the camera device 101 to the group ofregistered receiver entities (e.g., the user device 102, the live streammodule 121, the upload service module 130, the thumbnail service module140), as described more fully below.

In some examples, the gateway device 111 may send an image(s)/video(s)streamed/received from the camera device 101 to the computing device104. In some other examples, the computing device 104 may receive acontent stream of an image(s)/video(s) (and associated audio) from thecamera device 101. The computing device 104 may determine a number ofreceiver entities registered for the authentication service and mayduplicate/copy the content stream based on the number/quantity ofregistered receiver entities. The computing device 104 may sendduplicated copies of the content stream to each of the registeredreceiver entities (e.g., the user device 102, live stream module 121,the upload service module 130, the thumbnail service module 140), asdescribed more fully below.

The user device 102 may be a communication device such as, for example,a computer, a smartphone, a laptop, a smart tablet, a set top box, orother device configured to communicate with the gateway device 111, thecomputing device 104, the computing device 124 and the computing device134. The user device 102 may receive and/or transmit content between thegateway device 111, the computing device 104, the computing device 124and the computing device 134.

The user device 102 may comprise an interface 108 such as a userinterface or an application programming interface (API). As an example,the interface 108 may be configured to provide a visual presentation(e.g., via display 110), audio presentation, interactive communication,and the like. The interface 108 may comprise one or more interfaceelements that may comprise a keypad, menu, icon, user-selectable button,drop-down, slider bar, input field, and the like. One or more of theinterface elements may be configured to receive a selection or inputfrom a user.

The user device 102 may comprise a live stream module 121 (also referredto herein as live stream service 121, live stream service application121 or live stream service app 121). The user device 102 may be able todisplay content (e.g., live content of an image(s)/video(s) andassociated audio data) being streamed to the user device 102 (e.g., viathe live stream module 121) captured by a media capturing source (e.g.,camera device 101). The user device 102 may store (e.g., via processor112) the content captured from one or more media capturing sources instorage 106.

In some examples, based on detected input (e.g., keypad input) from auser via the interface elements, the user device 102 may register (e.g.,sign up) with an authentication service module (e.g., authenticationservice module 118) of computing device 104 as a receiver entity (e.g.,destination entity) of a designated group for receipt of contentstreamed to destination receiver entities (e.g., devices/servicesregistered with the authentication service module 118) of the group. Thecontent streamed may be a duplicate stream of a content stream (e.g., asingle stream of content of an image(s)/video(s) and associated data)captured by a media capturing source (e.g., camera device 101) of thegroup.

The computing device 124 may be a network device (e.g., a server)configured to communicate with gateway device 111, user device 102,computing device 104 and computing device 134, for example, via network105. The computing device 124 may include an upload service module 130(also referred to herein as upload service 130) that enables upload ofone or more images/videos and associated audio captured from one or moremedia capturing sources (e.g., camera device 101). The computing device124 may store (e.g., via processor 128) uploaded images/videos capturedfrom one or more media capturing sources (e.g., camera 101) in storage126. The images/videos stored in storage 126 may be accessible by a userdevice (e.g., user device 102) of a user.

The upload service module 130 may be registered with an authenticationservice module (e.g., authentication service module 118) of computingdevice 104 as a receiver entity (e.g., a destination receiver) of agroup (also referred to herein as groupcast group) for receipt ofgroupcast content streamed to destination devices/services (e.g.,devices/services registered with the authentication service module 118)of the group. The content stream may be a duplicate stream of a singlestream of content (e.g., an image(s)/video(s)) captured by a mediacapturing source (e.g., camera device 101) of the group.

The computing device 134 may be a network device (e.g., a server)configured to communicate with gateway device 111, user device 102,computing device 104 and computing device 124 for example via network105. The computing device 134 may include a thumbnail service module 140(also referred to herein as thumbnail service 140) that may provide oneor more thumbnail images and/or videos (e.g., reduced size images and/orvideos and associated audio) corresponding to one or more originalimages/videos (e.g., original/larger sized images/videos) captured by amedia capturing source (e.g., camera device 101). The computing device134 may store (e.g., via processor 138) the thumbnail images and/orvideos in storage 136. The thumbnail service module 140 may generate(e.g., via processor 138) a summary of the content associated with theone or more thumbnail images and/or videos and the summary may beannotated to the thumbnail images and/or videos.

The thumbnail service module 140 may be registered with anauthentication service module (e.g., authentication service module 118)of computing device 104 as a receiver entity (e.g., destination) of agroup for receipt of content streamed to destination devices/services(e.g., devices/services registered with the authentication servicemodule 118) of the group. The groupcast content stream may be aduplicate stream of a single stream of content (e.g., animage(s)/video(s)) captured by a media capturing source (e.g., cameradevice 101) of the group, as described more fully below. In someexamples, the update service module 130, the thumbnail service module140 and/or the live stream module 121 may be integrated in the computingdevice 104.

The computing device 104 may be a network device such as, for example, aserver configured to communicate with the user device 102, the computingdevice 124, the computing device 134, gateway device 111 and cameradevice 101. The computing device 104 may include an authenticationservice module 118 (also referred to herein as smart premises videogroup authentication service module 118) that may receive one or morerequests from one or more media capturing sources (also referred toherein as media capturing devices) (e.g., camera device 101) of apremises (e.g., premises 119) to register with the authentication module118 as a source of capturing content (e.g., image(s)/video(s) contentand associated audio data) for a group (e.g., a groupcast group).

Additionally, the computing device 104 may receive one or more requestsfrom devices/services (e.g., user device 102, live stream module 121,upload service module 130, thumbnail service module 140) to registerwith the authentication service module 118 as a receiver entity (e.g., adestination receiver) of the group for receipt of content streamcaptured from a registered media capturing source (e.g., camera device101).

The computing device 104 may provide group information associated withthe group to the gateway device 111. The group information may include,but is not limited to, an indication of a name of the group (e.g., agroupcast group), indications of one or more media capturing sources(e.g., camera device 101) of the group and associated network (e.g., IP)addresses as well as indications of one or more destination receivers(e.g., devices/services, for example, user device 102, upload servicemodule 130, thumbnail service module 140) of the group and associatednetwork (IP) addresses, as described more fully below.

In an instance in which a registered media capturing source (e.g.,camera device 101) captures content, the media capturing source may senda content stream (e.g., a single content stream) of the captured content(e.g., video content and associated audio data) to the gateway device111. The gateway device 111 may analyze the group information receivedfrom the computing device 104 and may determine the registereddestination devices/services (e.g., user device 102, live stream module121, upload service module 130, thumbnail service module 140) in thegroup. The gateway device 111 may duplicate the content of the streamreceived from the media capturing source (e.g., camera device 101) basedon a number/quantity of registered destination devices/services (e.g.,user device 102, live stream module 121, upload service module 130,thumbnail service module 140) and may provide the duplicated copies ofcontent to each of the registered destination devices/services of thegroupcast group. The gateway device 111 may send the duplicate copies tothe registered destination receivers simultaneously.

In some examples, the gateway device 111 may send the content stream(e.g., a single content stream) captured and received from the mediacapturing source (e.g., camera device 101) to the computing device 104(e.g., a network device). In some other examples, the media capturingsource (e.g., camera device 101) may send the content stream to thecomputing device. The computing device 104 may determine the registereddestination devices/services (e.g., user device 102, live stream module121, upload service module 130, thumbnail service module 140) in thegroupcast group. The computing device 104 may duplicate the contentstream received from the media capturing source (e.g., camera device101) based on a number/quantity of registered destinationdevices/services (e.g., user device 102, live stream module 121, uploadservice module 130, thumbnail service module 140) and may provide theduplicated copies of content to each of the registered destinationdevices/services of the group (e.g., the groupcast group).

Referring now to FIG. 2, an exemplary authenticated groupcast system andmethod is provided. At step 1, one or more media capturing sources(e.g., camera 101) of a premises (e.g., premises 119) and one or morereceiving entities (e.g., destination devices/services such as, forexample live stream service 121, upload service 130, thumbnail service140, user device 102, etc.) may register with the smart premises videogroup authentication service module 118 for inclusion in a designatedgroupcast group (e.g., a group designated/named as groupcast1). In someexamples, the registration of the one or more media capturing sourcesand receiving entities with the smart premises video groupauthentication service module 118 may be associated with an account of auser associated with a premises (e.g., premises 119). The account mayinclude a user profile and may include one or more credentials (e.g., ausername and/or password to log into the account) that allow the user aswell as the media capturing sources and receiving entities to beauthenticated to access the smart premises video group authenticationservice module 118.

An example of a registration request header and body for one or moremedia capturing sources and one or more destination receiving entities(e.g., devices/services) is provided below, which may include, forexample, a service authorization token (SAT) authorizing a service(e.g., the upload service 130, the thumbnail service 140, etc.) toregister with, and access, the smart premises video group authenticationservice module 118 and a JavaScript Object Notation (JSON) Web Token(JWT) authorizing another service (e.g., the live stream service 121) toregister with, and access, the smart premises video group authenticationservice module 118.

Header: { Authorization: ${SAT token}/${JWT token}, ... } Body: { type:Service/Device, id: Service Unique Name / Device Id, destination:true/false, privateIPv4: x.x.x.x, publicIPv4: x.x.x.x, IPv6: xxxx,groupName: groupcast1, groupIP: x.x.x.233 ... }

As shown in the body of the registration request above, the type ofservice(s)/device(s) (e.g., upload service 130, thumbnail service 140,live stream service 121, user device 102, etc.) as well as associatedidentifiers (e.g., an identifier (Id) associated with a Service UniqueName and/or Device Id) may be included. The designated group name (e.g.,groupcast1) of the groupcast group that the one or more media capturingsources and receiving entities are requesting to join may also beincluded in the registration request.

At step 2, the gateway device 111 may receive/fetch group informationfrom the smart premises video group authentication service module 118.For purposes of illustration and not of limitation, an example of thegroup information received by the gateway device 111 from the smartpremises video group authentication service module 118 is providedbelow.

Group Information { groupName: groupcast1, groupIP: x.x.x.233 (privateIP within reserved IP ranges) groupSources: [  { sourceName: camera1,sourceIPv4: x.x.x.x (private IP only), sourceIPv6: xxxx  },  {sourceName: camera2, sourceIPv4: x.x.x.x(private IP only), sourceIPv6:xxxx  },  ...  ],  groupDestinations: [  { destinationId: 1,destinationName: thumbnail service, destinationIPv4: x.x.x.x (PublicIP), destinationIPv6: xxxx  }, { destinationId: 2, destinationName:my-user device, destinationIPv4: x.x.x.x (Public IP), destinationIPv6:xxxx  },  ... ] }

As indicated above, the group information received by the gateway device111 from the smart premises video group authentication service module118 may indicate to the gateway device 111 one or more media capturingsources (e.g., camera 101) and one or more destination receiver entities(e.g., destination devices/services such as, for example, a thumbnailservice, a user device, etc.) that registered with the smart premisesvideo group authentication service module 118.

The group information received by the gateway device 111 may alsoindicate that the registered media capturing sources and registereddestination receiver entities are part of the same groupcast group(e.g., designated/named as groupcast1) and that the registered mediacapturing sources and registered destination entities share the samegroup network subnet address (e.g., the same group IP subnet addresssuch as, for example, x.x.x.233).

At step 3, a registered media capturing source (e.g., camera 101) maysend content of a captured image(s)/video(s) and associated audio and adatagram (e.g., a video datagram) in a content stream (e.g., a singlecontent stream) to the gateway device 111. The datagram sent from themedia capturing source (e.g., camera 101) to the gateway device 111 mayhave the data structure shown in FIG. 3.

As shown in FIG. 3, the datagram has a data structure 300 including anIP header, a User Datagram Protocol (UDP) header, an application headerand a payload. Referring to FIG. 4, an example IP header of a datagramis shown. The IP header 400 of the datagram, generated by the registeredmedia capturing source (e.g., camera 101), may have a new designatedconfiguration for the group IP address associated with ClasslessInter-Domain Routing (CIDR) and the options data.

With respect to the destination Group IP address portion of the IPheader 400, instead of including a normal individual destination IPaddress (e.g., a public IP address), the registered media capturingsource (e.g., camera 101) may include a private group IP address (e.g.,172.168.0.230/28) in the IP header 400. The private group IP address maybe associated with a private network (e.g., a home network, a businessnetwork, etc.).

The gateway device 111 may reserve the private IP CIDR from x.x.x.230/28as private group IP addresses for groupcast groups. For example, in aninstance in which the gateway device 111 has its own private IP addressas 172.168.0.1, when another device connects to the gateway device 111,the other device may be assigned, by the gateway device 111, any local(e.g., private) IP address from 172.168.0.2-172.168.0.229. The otherprivate IP addresses from 172.168.0.230-172.168.0.255 may be reserved,by the gateway device 111, as the group IP addresses (e.g., forgroupcast groups).

The options data of the IP header 400 may have the data structure 500shown in FIG. 5. The gateway device 111 may generate a network addresstranslation (NAT) table for the group IP addresses. The gateway device111 may run/execute a loop to check each instance of a group IPaddress(es) in the NAT table and may translate the group IP addresses tocorresponding individual destination IP addresses as shown in the table600 of FIG. 6.

In the example of FIG. 6, a group of destination receiver entitiesassociated with a designated groupcast group (e.g., groupcast1) mayshare the same group IP address (e.g., 172.168.0.233) corresponding toindividual destination IP addresses (e.g., 69.252.80.75, 96.114.14.140,71.230.36.162) associated with the destination receiver. For purposes ofillustration and not of limitation, as an example, individualdestination IP address 69.252.80.75 may be associated with a destinationservice such as, for example, thumbnail service 140, individualdestination IP address 96.114.14.140 may be associated with adestination service such as, for example, upload service 130, andindividual destination IP address 71.230.36.162 may be associated with adestination device such as, for example, user device 102.

FIG. 6 may also relate to a destination receiver entity associated withanother designated groupcast group (e.g., groupcast2) that may share thesame group IP address (e.g., 172.168.0.235) corresponding to one or moreindividual destination IP addresses (e.g., 68.87.41.40 associated with adestination service such as, for example, live stream service 121) of adestination receiver(s) entity of the group.

In an instance in which there are N individual destination IP addresses,for example, the group destination length=N in the group information(e.g., received from smart premises video group authentication servicemodule 118), then N copies of a datagram (e.g., a datagram received froma media capturing source (e.g., camera 101) may be generated, forexample, by the gateway device 111 and/or computing device 104) and therespective individual destination IP addresses may be designated toreplace the corresponding group IP addresses in an IP header (e.g., IPheader 400).

In this regard, in the example of FIG. 6, the gateway device 111 maydetermine that N=3 since there are 3 individual destination IP addresses(e.g., 69.252.80.75, 96.114.14.140, 71.230.36.162) for the group IPaddress 172.168.0.233. As such, the gateway device 111 may generate 3(e.g., N=3) copies of the datagram received in the content stream (e.g.,a single content stream) from a registered media capturing source (e.g.,camera 101).

Referring to back FIG. 2, at step 4, the gateway device 111 maysend/stream a copy (e.g., a groupcast stream) of a datagram to eachdestination receiver entity. As an example, the gateway device 111 maydetermine the destination receiver entities (e.g., destinationservice(s)/device(s)) in the datagram (e.g., video datagram) receivedfrom a media capturing source(s) (e.g., camera 101) and may duplicatethe datagram to generate multiple copies (N=3) for the destinationreceiver entities. The gateway device 111 may then send/stream the copyof the datagram to each destination receiver entity (e.g., thumbnailservice 140, upload service 130, user device 102) of a designatedgroupcast group (e.g., groupcast1).

In some examples, the computing device 104 (e.g., a network device) maydetermine the destination receiver entities (e.g., destinationservice(s)/device(s)) in the datagram streamed from a media capturingsource(s) (e.g., camera 101) and may duplicate the datagram to generatemultiple copies (N=3) for the destination receiver entities. Thecomputing device 104 may stream a copy of the datagram to eachdestination receiver entity (e.g., thumbnail service 140, upload service130, user device 102) of the designated groupcast group (e.g.,groupcast1).

As an example of providing an authenticated groupcast stream of contentto one or more destination receivers consider the following. A camera(e.g., a new camera such as, for example, camera 101) may be added to apremises (e.g., premises 119) and connected (e.g., via WiFi, Bluetooth,etc.) to a gateway device (e.g., gateway device 111). The gateway devicemay assign a new private IP address such as, for example, 172.168.0.5 tothe camera. The camera may be connected to a network (e.g., network 105)in response to connecting with the gateway device and may register(e.g., a provider premises registration) with an account of a userassociated with a premises (e.g., premises 119). The account may bemaintained by a content provider (e.g., a cable provider, a satelliteprovider, etc.) providing services (e.g., home security, TVsubscription, Internet, etc.) to the premises (e.g., premises 119).Based on registering with the account of the user associated with thepremises, other devices associated with (e.g., other registered devices)the account may be informed by a computing device (e.g., computingdevice 104) that a new device such as, for example, the camera (e.g.,camera 101) is included in, or associated with, the account of the user.

The camera may also generate a registration request to register with asmart premises video group authentication service, which is alsoassociated with the account of the user, to join a groupcast group(e.g., a new groupcast group). The smart premises video groupauthentication service may be provided by the smart premises video groupauthentication service module 118. The camera may generate and send aregistration request (e.g., a Hypertext Transfer Protocol (HTTP) postrequest) to the smart premises video group authentication service module118.

An example of the registration request generated and sent by the camerato the smart premises video group authentication service module 118 isas follows.

Header: { Authorization: ${JWT token}, ... }The JWT token includes the encrypted camera device id, account id.

Body: { type: Device, id: 6641230860435111412, destination: false,privateIPv4: 172.168.0.5 publicIPv4: 71.230.36.162, IPv6:2601:45:8100:c1d:1ea:2408:1a6:5cf9, groupName: groupcast1, groupIP: nullTTLs: 3600 }

The groupIP null may denote that this is a new group request and thesmart premises video group authentication service module 118 may send anew group private IP response to the camera. The destination may beidentified in the registration request as false since this is a newgroup request and no destination receiver entity may have registered tojoin the new group yet. An example of the response sent by the smartpremises video group authentication service module 118 to the camera(e.g., camera 101) is as follows.

Response:

HTTP status code=200Response Body={groupIP: 172.168.0.233: state: 0}

The camera may receive the response from the smart premises video groupauthentication service module 118. The state value may be a number toidentify a number/quantity of destination receiving entities (e.g.,destination devices/services) that have joined the group. In thisexample, since this is a request to join a new group, the state value is0 denoting to the camera that there are no destination receivingentities that have joined this group yet.

The smart premises video group authentication service module 118 maysend an updating event to a queue which may be received by (or otherwiselistened to by) one or more services or devices of a network (e.g.,network 105). The updating event may trigger one or more of the servicesand/or devices to register to the new group as a destination receivingentity associated with the account of the user.

As an example, the updating event may trigger a service such as, forexample, an upload service 130 to register to join the new group (e.g.,a groupcast group) as a destination receiving entity to receivegroupcast stream. In this example, the upload service module 130 maygenerate a registration request (e.g., a HTTP post request) including aheader and body as follows.

Header: { Authorization: ${SAT token}, ... } Body: { type: Service, id:2908757376510572177, destination: true, privateIPv4: null publicIPv4:96.114.14.140, IPv6: 2601:45:8100:c1d:1ea:2408:1a6:5ffc, groupName:groupcast1, groupIP: 172.168.0.233 TTLs: 3600 }

The SAT token in the registration request, generated by the uploadservice 130, may be a service to service authorization token which mayinclude a service id associated with the upload service 130. In the postbody, the type is indicated as “service” and the id may be the serviceaccount id of the user (e.g., a user associated with a premises such as,for example, premises 119). The service account id may be an encryptedaccount id that may be one-to-one mapped to the account id of the userassociated with the smart premises video group authentication servicemodule 118. The privateIPv4 is null since this is a service. The groupIP address is “172.168.0.233” which may be identified, by the uploadservice module 130 from the updating event in the queue. The destinationmay be identified as true since the upload service 130 is requestingregistration as a destination receiving entity (also referred to hereinas destination receiver entity).

In an instance in which the service registration succeeds, a response(e.g., a HTTP response) with a status code may be returned/sent from thesmart premises video group authentication service module 118 to theupload service 130. In this example, the response (e.g., a HTTPresponse) body may indicate {groupIP: 172.168.0.233: state: 1} denotingthat the registered upload service 130 has a group destination IPaddress of 172.168.0.233 and a state value of 1 indicating that there isone destination receiving entity (e.g., the upload service 130) in thegroup. The smart premises video group authentication service module 118may also send a broadcast notification to each registered source(s)(e.g., camera 101) and destination receiving entity in the group.

Based on the camera receiving the broadcast notification, the camera maybe informed that a new destination receiving entity (e.g., uploadservice 130) was added to the group. One or more other destinationreceiver entities (e.g., destination devices and/or services (e.g.,thumbnail service 140, live stream service 121, user device 102, etc.)may be added to the group in a similar manner as the upload service 130described above. For instance, in some examples the updating event sentby the smart premises video group authentication service module 118 maytrigger all devices of a predefined type (e.g., cell phones, smarttablets, laptops, etc.) of a network (e.g., e.g., network 105) toregister to join the new group as destination receiving entities toreceive groupcast stream. When the destination receiving entities (e.g.,destination services and/or devices) are set for the group, the cameramay capture content (e.g., an image(s)/video(s) and associated audio)and may begin streaming the content.

The camera may provide a content stream (e.g. a single content stream)with a destination indicated as a group destination IP address. Thestream may include a datagram (e.g., a video datagram) having an IPheader 700 as shown in FIG. 7. As shown in FIG. 7, the group destinationIP address is 172.168.0.233. In the options data, the camera may set thefirst bit as 1 to specify/denote that the options need copying in aninstance in which there are fragments (e.g., fragments/segments of avideo datagram) to keep such that information is not lost. The fragmentsthat are kept (e.g., stored) may allow a receiver to determine themanner in which to reassemble the fragments into a datagram (e.g., avideo datagram). The camera may also set the fifth bit as 1 in theoptions data to specify that the “172.168.0.5” in the options data isthe stream id used to identify the stream source (e.g., camera 101). The“110” in the options data denotes the length of the options (6 bytes inthis example) and the options data indicates the source IP address172.168.0.5 to specify the source (e.g., camera 101) of the stream, aspointed out above. In some examples, the options data may be in aTransport Control Protocol (TCP) segment or an User Datagram Protocol(UDP) segment.

The camera may send the stream to a communication device (e.g., gatewaydevice 111, computing device 104). The communication device (e.g.,gateway device 111, computing device 104) may include a network addresstranslator (NAT) configured to translate the group destination IPaddress (e.g., 172.168.0.5) to one or more individual destination IPaddresses (e.g., 69.252.80.75, 96.114.14.140, 71.230.36.162,68.87.41.40). The communication device (e.g., gateway device 111,computing device 104) may also make/generate multiple copies of adatagram (e.g., video datagram) in the stream, as described more fullybelow. In some examples, in an instance in which the options data arenot set (e.g., the camera set the first bit of the options as 0), thestream received from the camera may be determined by the communicationdevice (e.g., gateway device 111, computing device 104) as a normalsingle stream without requiring datagram duplications/copies.

The communication device (e.g., gateway device 111, computing device104) may analyze the options data in an IP header (e.g., IP header 700)of a datagram (e.g., a video datagram) in stream received from thecamera and may translate a destination field (e.g., a group IPdestination address(es) such as, for example, 172.168.0.233) into one ormore individual destination IP addresses as indicated in the data oftable 800 (e.g., a NAT table 800) shown in FIG. 8.

Based in part on evaluating the data associated with table 800, thecommunication device (e.g., gateway device 111, computing device 104)may determine that there are three entries/instances associated with thegroup IP destination address 172.168.0.233. In this regard, thecommunication device (e.g., gateway device 111, computing device 104)may determine that there are N (e.g., N=3) individual IP destinationaddresses (e.g., the group destination length=N) and as such thecommunication device (e.g., gateway device 111, computing device 104)may make/generate three (e.g., N=3) duplicates/copies of a datagram(e.g., a video datagram) received in the stream from the camera. Thecontent (e.g., image(s)/video(s) and associated audio) captured by thecamera (e.g., camera 101) may be included in a payload (e.g., thepayload of FIG. 3) of the datagram streamed from the camera. Thecommunication device (e.g., gateway device 111, computing device 104)may similarly include the content captured by the camera in the payloadof the duplicated datagrams. In generating the duplicates/copies of thedatagram, the communication device (e.g., gateway device 111, computingdevice 104) may replace the group destination IP address (e.g.,172.168.0.233) in an IP header (e.g., IP header 700) of a datagram witha destination IP address (e.g., 69.252.80.75) corresponding to adestination receiving entity (e.g., thumbnail service 140) for each ofthe duplicated/copied datagrams. Examples of each of the threeduplicated datagram IP headers (e.g., IP header 900, IP header 1000, IPheader 1100), generated by a communication device (e.g., gateway device111, computing device 104) are shown in FIGS. 9, 10 and 11.

In the IP headers 900, 1000 and 1100, the options data 00000001 maydenote for the set of options data (e.g., 00000001 00000000) that nooperations are needed. As such, any additional gateway devices on a pathto a destination receiver entity may forward a datagram normally withoutany additional operations/duplications.

As shown in FIG. 9, in the IP header 900 the destination IP address is69.252.80.75, which may correspond to a destination receiver entity suchas, for example, thumbnail service 140 of a groupcast group (e.g.,groupcast group 1). As shown in FIG. 10, in the IP header 1000 thedestination IP address is 96.114.14.140, which may correspond to adestination receiver entity such as for example, upload service 130, ofthe groupcast group. As shown in FIG. 11, in the IP header 1100 thedestination IP address is 71.230.36.162, which may correspond to adestination receiver entity such as, for example, user device 102 of thegroupcast group.

The communication device (e.g., gateway device 111, computing device104) may send each duplicated datagram in a stream (e.g., a groupcaststream) to a corresponding destination (e.g., destination receiverentity). For example, regarding the example above with respect to FIGS.9-11, the communication device (e.g., gateway device 111, computingdevice 104) may send a stream with a duplicate datagram (e.g.,associated with the datagram sent from the camera) including the IPheader 900 to a destination (e.g., destination receiver entity) such as,for example, thumbnail service 140. The communication device (e.g.,gateway device 111, computing device 104) may also send a stream with aduplicate datagram (e.g., associated with the datagram sent from thecamera) including the IP header 1000 to a corresponding destination(e.g., destination receiver entity) such as, for example, upload service130. The communication device (e.g., gateway device 111, computingdevice 104) may also send a stream with a duplicate datagram (e.g.associated with the datagram sent from the camera) including the IPheader 1100 to a corresponding destination (e.g., destination receiverentity) such as, for example, user device 102.

FIG. 12 illustrates an example method for providing an authenticatedgroupcast stream of content to destination receivers. In operation 1202,a communication device (e.g., gateway device 111) may receiveinformation (e.g., group information) indicating that a media capturesource(s) (e.g., camera 101) located at a premises (e.g., premises 119)and one or more destination entities (e.g., destination devices and/orservices such as, for example, user device 102, upload service module130, thumbnail service module 140, live stream module 121, etc.) areincluded in a group (e.g., groupcast1). In some examples, theinformation may be received based on the media capturing source(s) andthe one or more destination receiver entities registering with a service(e.g., smart premises video group authentication service module 118).

In operation 1204, a communication device (e.g., gateway device 111) mayreceive, from the media capture source(s) (e.g., camera device 101),content (e.g., in a datagram) including a captured image and/or video(and associated audio) and an indication of a destination network (e.g.,an IP address. The destination network address (e.g., 172.168.0.233) maybe associated with the one or more destination entities of the group.The destination network address (e.g., 172.168.0.233) may be used, bythe communication device, to determine one or more network addresses(e.g., 69.252.80.75, 96.114.14.140, 71.230.36.162) of the one or moredestination entities.

In operation 1206, a communication device (e.g., gateway device 111) maycreate one or more copies of the content. The number/quantity (e.g., 4)of copies may correspond to a number/quantity (e.g., 4) of the one ormore destination entities (e.g., user device 102, upload service module130, thumbnail service module 140, live stream module 121) of the groupdetermined to receive the content. In operation 1208, a communicationdevice (e.g., gateway device 111) may send to the determined one or moredestination entities a respective copy of the copies of the content. Thedestination network address may be a group private IP address and therespective (e.g., individual) network addresses may be destinationprivate IP addresses. In some examples, the destination entities mayrelate to devices and/or services. As an example, the services maycomprise one or more image or video provision services (e.g., uploadservice 130, thumbnail service 140, live stream service 121). In otherexamples, the devices may relate to a type of device (e.g., a cell phonesuch as, for example, a make/model of a cell phone, a smart tablet suchas, for example, a make/model of a smart tablet, a laptop such as, forexample, a make/model of a laptop, etc.). In other examples, the devicesmay be any suitable communication devices irrespective of the type ofdevice.

FIG. 13 illustrates an example method for providing an authenticatedgroupcast stream of content to destination receivers. In operation 1302,a communication device (e.g., gateway device 111, computing device 104)may receive, from at least one media capture source (e.g., camera device101), content (e.g., a single stream of content in a datagram) includinga captured image and/or video (and associated audio) and an indicationof a destination network (e.g., IP) address (e.g., 172.168.0.233)associated with one or more destination entities (e.g., upload servicemodule 130, thumbnail service module 140, live stream module 121) of agroup (e.g., groupcast1). The destination network address may be used,by the communication device, to determine one or more network addressesof the one or more destination entities.

In operation 1304, a communication device (e.g., gateway device 111,computing device 104) may create one or more copies of the content. Thenumber/quantity (e.g., 3) of copies may correspond to a number/quantity(e.g., 3) of the network (e.g., IP) addresses of the one or moredestination entities of the group determined to receive the content. Forpurposes of illustration, and not of limitation, the network addresses(e.g., 69.252.80.75, 96.114.14.140, 71.230.36.162) may be associatedwith one or more destination entities such, as for example, uploadservice module 130, thumbnail service module 140, live stream module121, etc.

In operation 1306, a communication device (e.g., gateway device 111,computing device 104) may send to the determined one or more destinationentities a respective copy of the copies of the content. In someexamples, the communication device may determine the one or moredestination entities based in part on analyzing the network addressesassociated with the destination entities. For example, analyzing thenetwork addresses may be based on the communication device evaluatingdata of a NAT table (e.g., table 800 of FIG. 8).

FIG. 14 illustrates another example method for providing anauthenticated groupcast stream of content to destination receivers. Inoperation 1402, a communication device (e.g., computing device 104) mayreceive one or more requests (e.g., a HTTP post request) from at leastone media capture source (e.g., camera device 101) and one or moredestination entities (e.g., upload service module 130, thumbnail servicemodule 140, live stream module 121, user device 102) to register with aservice (e.g., smart premises video group authentication service 118)and to join a group (e.g., groupcast1).

In operation 1404, a communication device (e.g., computing device 104)may receive content (e.g., a single stream) captured from the at leastone media capture source (e.g., camera 101). In some examples, thecommunication device (e.g., computing device 104) may receive thecontent in response to being provided the content from the media capturesource(s) (e.g., camera 101). In other examples, the communicationdevice may receive the content in response to being provided the contentfrom another device (e.g., gateway device 111). The content may include,but is not limited to, a captured image or video (and associated audio)and an indication of a destination network address (e.g., in a datagram)associated with the one or more destination entities of the group. Thedestination network address (e.g., 172.168.0.233) may be used, by thecommunication device, to determine one or more network addresses of theone or more destination entities.

In operation 1406, a communication device (e.g., computing device 104)may create one or more copies of the content. The number/quantity (e.g.,3) of copies may correspond to a number/quantity of the networkaddresses (e.g., 69.252.80.75, 96.114.14.140, 71.230.36.162), associatedwith the one or more destination entities of the group determined toreceive the content. The copying of the content may comprise inclusionof a datagram (e.g., a video datagram) including an IP header (e.g., IPheader 900, IP header 1000, IP header 1100, etc.), a UDP header, anapplication header and a payload (e.g., according to the data structure300 of FIG. 3).

In operation 1408, a communication device (e.g., computing device 104)may send to the determined one or more destination entities a respectivecopy of the copies of the content. In some examples, the communicationdevice may determine the destination entities based in part on analyzingthe network addresses (e.g., 69.252.80.75, 96.114.14.140, 71.230.36.162)associated with the destination entities (e.g., user device 102, uploadservice module 130, thumbnail service module 140, etc.) For example,analyzing the network addresses may be based on the communication deviceevaluating data of a NAT table (e.g., table 800 of FIG. 8).

FIG. 15 depicts an example computer system that includes or isconfigured to access one or more computer-accessible media such as, forexample, computing device 1500 capable of executing software forperforming operations as described above in connection with FIGS. 1-14.In the illustrated example embodiment, the computing device 1500 mayinclude one or more processors 1510 a, 1510 b, and/or 1510 n (which maybe referred herein singularly as the processor 1510 or in the plural asthe processors 1510) coupled to a system memory 1520 via an input/output(I/O) interface 1530. The computing device 1500 may further include anetwork interface 1540 coupled to an I/O interface 1530.

In various embodiments, the computing device 1500 may be a uniprocessorsystem including one processor 1510 or a multiprocessor system includingseveral processors 1510 (e.g., two, four, eight, or another suitablenumber). The processors 1510 may be any suitable processors capable ofexecuting instructions. For example, in various embodiments, theprocessor(s) 1510 may be special-purpose or embedded processorsimplementing any of a variety of instruction set architectures (ISAs),such as the x86, PowerPC, SPARC, or MIPS ISAs, or any other suitableISA. In multiprocessor systems, each of the processors 1510 maycommonly, but not necessarily, implement the same ISA.

In some embodiments, a graphics processing unit (“GPU”) 1512 mayparticipate in providing graphics rendering and/or physics processingcapabilities. A GPU may, for example, comprise a highly parallelizedprocessor architecture specialized for graphical computations. In someembodiments, the processors 1510 and the GPU 1512 may be implemented asone or more of the same type of device.

The system memory 1520 may be configured to store instructions and dataaccessible by the processor(s) 1510. In various embodiments, the systemmemory 1520 may be implemented using any suitable memory technology,such as static random access memory (“SRAM”), synchronous dynamic RAM(“SDRAM”), nonvolatile/Flash®-type memory, or any other type of memory.In the illustrated embodiment, program instructions and dataimplementing one or more desired functions, such as those methods,techniques and data described above, are shown stored within the systemmemory 1520 as code 1525 and data 1526.

In one embodiment, the I/O interface 1530 may be configured tocoordinate I/O traffic between the processor(s) 1510, the system memory1520 and any peripherals in the device, including a network interface1540 or other peripheral interfaces. In some embodiments, the I/Ointerface 1530 may perform any necessary protocol, timing or other datatransformations to convert data signals from one component (e.g., thesystem memory 1520) into a format suitable for use by another component(e.g., the processor 1510). In some embodiments, the I/O interface 1530may include support for devices attached through various types ofperipheral buses, such as a variant of the Peripheral ComponentInterconnect (PCI) bus standard or the Universal Serial Bus (USB)standard, for example. In some embodiments, the function of the I/Ointerface 1530 may be split into two or more separate components, suchas a north bridge and a south bridge, for example. Also, in someembodiments some or all of the functionality of the I/O interface 1530,such as an interface to the system memory 1520, may be incorporateddirectly into the processor 1510.

The network interface 1540 may be configured to allow data to beexchanged between the computing device 1500 and other device or devices1560 attached to a network or networks 1550, such as other computersystems or devices, for example. In various embodiments, the networkinterface 1540 may support communication via any suitable wired orwireless general data networks, such as types of Ethernet networks, forexample. Additionally, the network interface 1540 may supportcommunication via telecommunications/telephony networks, such as analogvoice networks or digital fiber communications networks, via storagearea networks, such as Fibre Channel SANs (e.g., storage area networks),or via any other suitable type of network and/or protocol.

In some embodiments, the system memory 1520 may be one embodiment of acomputer-accessible medium configured to store program instructions anddata as described above for implementing embodiments of thecorresponding methods and apparatus. However, in other embodiments,program instructions and/or data may be received, sent, or stored upondifferent types of computer-accessible media. Generally speaking, acomputer-accessible medium may include non-transitory storage media ormemory media, such as magnetic or optical media, e.g., disk or DVD/CDcoupled to computing device the 1500 via the I/O interface 730. Anon-transitory computer-accessible storage medium may also include anyvolatile or non-volatile media, such as RAM (e.g., SDRAM, DDR SDRAM,RDRAM, SRAM, etc.), ROM, etc., that may be included in some embodimentsof the computing device 1500 as the system memory 1520 or another typeof memory. Further, a computer-accessible medium may includetransmission media or signals, such as electrical, electromagnetic ordigital signals, conveyed via a communication medium, such as a networkand/or a wireless link, such as those that may be implemented via thenetwork interface 1540. Portions or all of multiple computing devices,such as those illustrated in FIG. 15, may be used to implement thedescribed functionality in various embodiments; for example, softwarecomponents running on a variety of different devices and servers maycollaborate to provide the functionality. In some embodiments, portionsof the described functionality may be implemented using storage devices,network devices or special-purpose computer systems, in addition to orinstead of being implemented using general-purpose computer systems. Theterm “computing device,” as used herein, refers to at least all thesetypes of devices and is not limited to these types of devices.

It should also be appreciated that the systems in the figures are merelyillustrative and that other implementations might be used. Additionally,it should be appreciated that the functionality disclosed herein mightbe implemented in software, hardware, or a combination of software andhardware. Other implementations should be apparent to those skilled inthe art. It should also be appreciated that a server, gateway, or othercomputing node may include any combination of hardware or software thatmay interact and perform the described types of functionality, includingwithout limitation desktop or other computers, database servers, networkstorage devices and other network devices, PDAs, tablets, cellphones,wireless phones, pagers, electronic organizers, Internet appliances,television-based systems (e.g., using set top boxes and/orpersonal/digital video recorders), and various other consumer productsthat include appropriate communication capabilities. In addition, thefunctionality provided by the illustrated modules may in some aspects becombined in fewer modules or distributed in additional modules.Similarly, in some aspects the functionality of some of the illustratedmodules may not be provided and/or other additional functionality may beavailable.

Each of the operations, processes, methods, and algorithms described inthe preceding sections may be embodied in, and fully or partiallyautomated by, code modules executed by at least one computer or computerprocessors. The code modules may be stored on any type of non-transitorycomputer-readable medium or computer storage device, such as harddrives, solid state memory, optical disc, and/or the like. The processesand algorithms may be implemented partially or wholly inapplication-specific circuitry. The results of the disclosed processesand process steps may be stored, persistently or otherwise, in any typeof non-transitory computer storage such as, e.g., volatile ornon-volatile storage.

The various features and processes described above may be usedindependently of one another, or may be combined in various ways. Allpossible combinations and sub-combinations are intended to fall withinthe scope of this disclosure. In addition, certain method or processblocks may be omitted in some implementations. The methods and processesdescribed herein are also not limited to any particular sequence, andthe blocks or states relating thereto may be performed in othersequences that are appropriate. For example, described blocks or statesmay be performed in an order other than that specifically disclosed, ormultiple blocks or states may be combined in a single block or state.The example blocks or states may be performed in serial, in parallel, orin some other manner. Blocks or states may be added to or removed fromthe disclosed example aspects. The example systems and componentsdescribed herein may be configured differently than described. Forexample, elements may be added to, removed from, or rearranged comparedto the disclosed example aspects.

It will also be appreciated that various items are illustrated as beingstored in memory or on storage while being used, and that these items orportions of thereof may be transferred between memory and other storagedevices for purposes of memory management and data integrity.Alternatively, in other aspects some or all of the software modulesand/or systems may execute in memory on another device and communicatewith the illustrated computing systems via inter-computer communication.Furthermore, in some aspects, some or all of the systems and/or modulesmay be implemented or provided in other ways, such as at least partiallyin firmware and/or hardware, including, but not limited to, at least oneapplication-specific integrated circuits (ASICs), standard integratedcircuits, controllers (e.g., by executing appropriate instructions, andincluding microcontrollers and/or embedded controllers),field-programmable gate arrays (FPGAs), complex programmable logicdevices (CPLDs), etc. Some or all of the modules, systems and datastructures may also be stored (e.g., as software instructions orstructured data) on a computer-readable medium, such as a hard disk, amemory, a network, or a portable media article to be read by anappropriate drive or via an appropriate connection. The systems,modules, and data structures may also be transmitted as generated datasignals (e.g., as part of a carrier wave or other analog or digitalpropagated signal) on a variety of computer-readable transmission media,including wireless-based and wired/cable-based media, and may take avariety of forms (e.g., as part of a single or multiplexed analogsignal, or as multiple discrete digital packets or frames). Suchcomputer program products may also take other forms in other aspects.Accordingly, the present disclosure may be practiced with other computersystem configurations.

Conditional language used herein, such as, among others, “may,” “could,”“might,” “may,” “e.g.,” and the like, unless specifically statedotherwise, or otherwise understood within the context as used, isgenerally intended to convey that certain aspects include, while otheraspects do not include, certain features, elements, and/or steps. Thus,such conditional language is not generally intended to imply thatfeatures, elements, and/or steps are in any way required for at leastone aspects or that at least one aspects necessarily include logic fordeciding, with or without author input or prompting, whether thesefeatures, elements, and/or steps are included or are to be performed inany particular aspect. The terms “comprising,” “including,” “having,”and the like are synonymous and are used inclusively, in an open-endedfashion, and do not exclude additional elements, features, acts,operations, and so forth. Also, the term “or” is used in its inclusivesense (and not in its exclusive sense) so that when used, for example,to connect a list of elements, the term “or” means one, some, or all ofthe elements in the list.

While certain example aspects have been described, these aspects havebeen presented by way of example only, and are not intended to limit thescope of aspects disclosed herein. Thus, nothing in the foregoingdescription is intended to imply that any particular feature,characteristic, step, module, or block is necessary or indispensable.Indeed, the novel methods and systems described herein may be embodiedin a variety of other forms; furthermore, various omissions,substitutions, and changes in the form of the methods and systemsdescribed herein may be made without departing from the spirit ofaspects disclosed herein. The accompanying claims and their equivalentsare intended to cover such forms or modifications as would fall withinthe scope and spirit of certain aspects disclosed herein.

The preceding detailed description is merely exemplary in nature and isnot intended to limit the disclosure or the application and uses of thedisclosure. The described aspects are not limited to use in conjunctionwith a particular type of machine. Hence, although the presentdisclosure, for convenience of explanation, depicts and describesparticular machine, it will be appreciated that the assembly andelectronic system in accordance with this disclosure may be implementedin various other configurations and may be used in other types ofmachines. Furthermore, there is no intention to be bound by any theorypresented in the preceding background or detailed description. It isalso understood that the illustrations may include exaggerateddimensions to better illustrate the referenced items shown, and are notconsider limiting unless expressly stated as such.

It will be appreciated that the foregoing description provides examplesof the disclosed system and technique. However, it is contemplated thatother implementations of the disclosure may differ in detail from theforegoing examples. All references to the disclosure or examples thereofare intended to reference the particular example being discussed at thatpoint and are not intended to imply any limitation as to the scope ofthe disclosure more generally. All language of distinction anddisparagement with respect to certain features is intended to indicate alack of preference for those features, but not to exclude such from thescope of the disclosure entirely unless otherwise indicated.

The disclosure may include communication channels that may be any typeof wired or wireless electronic communications network, such as, e.g., awired/wireless local area network (LAN), a wired/wireless personal areanetwork (PAN), a wired/wireless home area network (HAN), awired/wireless wide area network (WAN), a campus network, a metropolitannetwork, an enterprise private network, a virtual private network (VPN),an internetwork, a backbone network (BBN), a global area network (GAN),the Internet, an intranet, an extranet, an overlay network, a cellulartelephone network, a Personal Communications Service (PCS), using knownprotocols such as the Global System for Mobile Communications (GSM),CDMA (Code-Division Multiple Access), Long Term Evolution (LTE), W-CDMA(Wideband Code-Division Multiple Access), Wireless Fidelity (Wi-Fi),Bluetooth, and/or the like, and/or a combination of two or more thereof.

Additionally, the various aspects of the disclosure may be implementedin a non-generic computer implementation. Moreover, the various aspectsof the disclosure set forth herein improve the functioning of the systemas is apparent from the disclosure hereof. Furthermore, the variousaspects of the disclosure involve computer hardware that it specificallyprogrammed to solve the complex problem addressed by the disclosure.Accordingly, the various aspects of the disclosure improve thefunctioning of the system overall in its specific implementation toperform the process set forth by the disclosure and as defined by theclaims.

Recitation of ranges of values herein are merely intended to serve as ashorthand method of referring individually to each separate valuefalling within the range, unless otherwise indicated herein, and eachseparate value is incorporated into the specification as if it wereindividually recited herein. All methods described herein may beperformed in any suitable order unless otherwise indicated herein orotherwise clearly contradicted by context.

The methods and systems can employ artificial intelligence techniquessuch as machine learning and iterative learning. Examples of suchtechniques include, but are not limited to, expert systems, case basedreasoning, Bayesian networks, behavior based AI, neural networks, fuzzysystems, evolutionary computation (e.g. genetic algorithms), swarmintelligence (e.g. ant algorithms), and hybrid intelligent systems (e.g.expert inference rules generated through a neural network or productionrules from statistical learning).

While the methods and systems have been described in connection withpreferred embodiments and specific examples, it is not intended that thescope be limited to the particular embodiments set forth, as theembodiments herein are intended in all respects to be illustrativerather than restrictive.

Unless otherwise expressly stated, it is in no way intended that anymethod set forth herein be construed as requiring that its steps beperformed in a specific order. Accordingly, where a method claim doesnot actually recite an order to be followed by its steps or it is nototherwise specifically stated in the claims or descriptions that thesteps are to be limited to a specific order, it is no way intended thatan order be inferred, in any respect. This holds for any possiblenon-express basis for interpretation, including: matters of logic withrespect to arrangement of steps or operational flow; plain meaningderived from grammatical organization or punctuation; the number or typeof embodiments described in the specification.

It is to be understood that the terminology used herein is for thepurpose of describing particular embodiments only and is not intended tobe limiting.

As used in the specification and the appended claims, the singular forms“a,” “an,” and “the” include plural referents unless the context clearlydictates otherwise. Ranges may be expressed herein as from “about” oneparticular value, and/or to “about” another particular value. When sucha range is expressed, another embodiment includes from the oneparticular value and/or to the other particular value. Similarly, whenvalues are expressed as approximations, by use of the antecedent“about,” it will be understood that the particular value forms anotherembodiment. It will be further understood that the endpoints of each ofthe ranges are significant both in relation to the other endpoint, andindependently of the other endpoint.

“Optional” or “optionally” means that the subsequently described eventor circumstance may or may not occur, and that the description includesinstances where said event or circumstance occurs and instances where itdoes not.

Throughout the description and claims of this specification, the word“comprise” and variations of the word, such as “comprising” and“comprises,” means “including but not limited to,” and is not intendedto exclude, for example, other components, integers or steps.“Exemplary” means “an example of” and is not intended to convey anindication of a preferred or ideal embodiment. “Such as” is not used ina restrictive sense, but for explanatory purposes.

Disclosed are components that can be used to perform the disclosedmethods and comprise the disclosed systems. These and other componentsare disclosed herein, and it is understood that when combinations,subsets, interactions, groups, etc. of these components are disclosedthat while specific reference of each various individual and collectivecombination and permutation of these may not be explicitly disclosed,each is specifically contemplated and described herein, for all methodsand systems. This applies to all aspects of this application including,but not limited to, steps in disclosed methods. Thus, if there are avariety of additional steps that can be performed it is understood thateach of these additional steps can be performed with any specificembodiment or combination of embodiments of the disclosed methods.

The present methods and systems may be understood more readily byreference to the following detailed description of preferred embodimentsand the examples included therein and to the Figures and their previousand following description.

As will be appreciated by one skilled in the art, the methods andsystems may take the form of an entirely hardware embodiment, anentirely software embodiment, or an embodiment combining software andhardware aspects. Furthermore, the methods and systems may take the formof a computer program product on a computer-readable storage mediumhaving computer-readable program instructions (e.g., computer software)embodied in the storage medium. More particularly, the present methodsand systems may take the form of web-implemented computer software. Anysuitable computer-readable storage medium may be utilized including harddisks, CD-ROMs, optical storage devices, or magnetic storage devices.

Embodiments of the methods and systems are described herein withreference to block diagrams and flowchart illustrations of methods,systems, apparatuses and computer program products. It will beunderstood that each block of the block diagrams and flowchartillustrations, and combinations of blocks in the block diagrams andflowchart illustrations, respectively, can be implemented by computerprogram instructions. These computer program instructions may be loadedonto a computer, special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructionswhich execute on the computer or other programmable data processingapparatus create a means for implementing the functions specified in theflowchart block or blocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including computer-readableinstructions for implementing the function specified in the flowchartblock or blocks. The computer program instructions may also be loadedonto a computer or other programmable data processing apparatus to causea series of operational steps to be performed on the computer or otherprogrammable apparatus to produce a computer-implemented process suchthat the instructions that execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

Accordingly, blocks of the block diagrams and flowchart illustrationssupport combinations of means for performing the specified functions,combinations of steps for performing the specified functions and programinstruction means for performing the specified functions. It will alsobe understood that each block of the block diagrams and flowchartillustrations, and combinations of blocks in the block diagrams andflowchart illustrations, can be implemented by special purposehardware-based computer systems that perform the specified functions orsteps, or combinations of special purpose hardware and computerinstructions.

It will be apparent to those skilled in the art that variousmodifications and variations can be made without departing from thescope or spirit. Other embodiments will be apparent to those skilled inthe art from consideration of the specification and practice disclosedherein. It is intended that the specification and examples be consideredas exemplary only, with a true scope and spirit being indicated by thefollowing claims.

1. A method comprising: receiving information indicating that at leastone media capture source, located at a premises, and one or moredestination entities are included in a group; receiving, from the atleast one media capture source, content comprising at least one of acaptured image or video and an indication of a destination networkaddress associated with the one or more destination entities of thegroup, wherein the destination network address is used to determine oneor more network addresses of the one or more destination entities;determining a number of copies of the content based on determining anumber of the network addresses, associated with the one or moredestination entities, that are determined from the destination networkaddress, wherein the number of the one or more copies correspond to anumber of the one or more destination entities of the group determinedto receive the content; creating one or more copies of the content basedon the determined number of copies; and sending to the determined one ormore destination entities a respective copy of the one or more copies ofthe content.
 2. (canceled)
 3. The method of claim 1, wherein creatingthe one or more copies further comprises: replacing, in the copies, thedestination network address with a respective network address associatedwith a corresponding destination entity of the destination entities. 4.The method of claim 1, wherein creating the one or more copies comprisesduplicating the content to create the number of the copies correspondingto the number of the destination entities determined to receive thecontent.
 5. The method of claim 4, further comprising: performing theduplicating based on detecting data in a set of options data in thecontent indicating to copy the content.
 6. The method of claim 1,wherein the received information indicates that the media capture sourceand the destination entities are registered with a service.
 7. Themethod of claim 1, wherein determining the network addresses comprisesgenerating a network address translation of the destination networkaddress to respective network addresses associated with the destinationentities.
 8. The method of claim 1, wherein receiving informationfurther comprises receiving the information based on the at least onemedia capture source and the one or more destination entities generatingrequests to register with a service and being authenticated by theservice to join the group.
 9. The method of claim 5, wherein the contentcomprises the destination network address and the set of options in aheader of a datagram of the content.
 10. The method of claim 1, whereinthe media capture source comprises a camera device or a video recordingdevice.
 11. The method of claim 1, wherein the one or more destinationentities comprise one or more devices or services.
 12. The method ofclaim 11, wherein the services comprise one or more image or videoprovision services.
 13. A method comprising: receiving, from at leastone media capture source, content comprising at least one of a capturedimage or video and an indication of a destination network addressassociated with one or more destination entities of a group, wherein thedestination network address is used to determine one or more networkaddresses of the one or more destination entities; determining a numberof copies of the content based on determining a number of the networkaddresses, associated with the one or more destination entities, thatare determined from the destination network address, wherein the numberof the one or more copies correspond to a number of the one or moredestination entities of the group determined to receive the content;creating one or more copies of the content based on the determinednumber of copies; and sending to the determined one or more destinationentities a respective copy of the one or more copies of the content. 14.The method of claim 13, wherein creating the number of copies furthercomprises: replacing, in the copies, the destination network addresswith a respective network address associated with a correspondingdestination entity of the destination entities.
 15. The method of claim13, further comprising: creating the one or more copies based ondetecting data in a set of options data in the stream of contentindicating to copy the content.
 16. The method of claim 13, wherein thecomputing device is located at the premises.
 17. The method of claim 13,wherein the destination network address comprises a destination privateInternet Protocol (IP) address and the network addresses comprisedestination private IP addresses.
 18. A method comprising: receiving oneor more requests from at least one media capture source and one or moredestination entities to register with a service and to join a group;receiving content from the at least one media capture source, thecontent comprising at least one of a captured image or video and anindication of a destination network address associated with the one ormore destination entities of the group, wherein the destination networkaddress is used to determine one or more network addresses of the one ormore destination entities; determining a number of copies of the contentbased on determining a number of the network addresses, associated withthe one or more destination entities, that are determined from thedestination network address, wherein the number of the one or morecopies correspond to a number of the one or more destination entities ofthe group determined to receive the content; creating one or copies ofthe content based on the determined number of copies; and sending to thedetermined one or more destination entities a respective copy of the oneor more copies of the content.
 19. The method of claim 18, wherein priorto receiving the content, the method further comprises: determining thatthe at least one media capture source and the one or more destinationentities are authenticated by the service.
 20. The method of claim 18,wherein creating the one or more copies further comprises: replacing, inthe copies, the destination network address with a respective networkaddress associated with a corresponding destination entity of thedestination entities.
 21. The method of claim 18, further comprising:creating the one or more copies based on detecting data in a set ofoptions data in a datagram of the content indicating to copy thecontent.
 22. The method of claim 18, wherein the computing devicecomprises a network device located external to the premises.